EVALUATION RESULTS
The FDIC Has Established Contract Rationalization Mechanisms
The FDIC has established informal processes to evaluate new procurement requests for potential duplication and existing contracts for continuing need. The FDIC relies on the knowledge of its two ASB Associate Directors as the primary mechanism to evaluate whether new procurement requests could be met by active contracts and whether there is a continuing need for existing contracts. ASB management also meets on a regular basis to review workload status, including pre- and post-award contract activity. ASB also communicates with the program offices and uses NFE reports to make procurement consolidation and elimination decisions. Nonetheless, such reliance on a limited number of individuals can present continuity risks in the event that the individuals separate from the Corporation.
Evaluating New Procurement Requests
The FDIC recognizes the need for strong planning during the procurement of goods and services. The APM discusses the benefits of early communication between the program office and ASB during acquisition planning efforts. The APM, among other things, states that early communication allows ASB to identify upcoming requirements and plan how to meet them, work with program offices to finalize statements of work, and combine duplicative requirements for similar services.
When initial requests for new contract work are submitted to ASB, the Associate Directors make an assessment based on first-hand knowledge and consultation with the program offices as to whether the requests can be fulfilled using existing contracts. For example, the FDIC used its In-bound Call Center contract, which exists to provide resources for the FDIC Central Call Center, during Hurricane Katrina. Rather than awarding a new contract, the FDIC was able to use the existing In-bound Call Center contract to establish a call center for Gulf Coast residents because the services needed were within the scope of that contract. The FDIC also responded to a request for benchmarking services from the Division of Finance by expanding the scope of an existing DRR nationwide benchmarking services contract.
Determining Continuing Need
We discussed with ASB management the mechanisms they have in place to determine the continuing need for contracts. ASB officials indicated that ASB staff meet on a regular basis to review and discuss workload status and the continuing need for active contracts using the monthly Management Data Report. The monthly Management Data Report provides information regarding outstanding requisitions and contracts awarded by ASB.
ASB officials indicated that they also rely on continual input from the program offices to assess whether there is a continuing need for a contract. Specifically, once a contract has been awarded, the Associate Director and program officials meet on a regular basis to discuss the program offices’ future contracting needs. If the work will be completed by the expiration date of the contract, the contract will be allowed to expire. If there are future needs for the contract, ASB will determine whether the contract should be extended or recompeted. This information is then compiled in a spreadsheet and sorted by contract expiration date. If different program offices have contracts involving similar services expiring in the same general period, the Associate Director will discuss with the program offices involved whether the requirements can be combined into one contract.
We discussed with ASB officials the risks associated with allowing dormant contracts and task orders to remain active in NFE once contract work has been completed or the contract is no longer needed. ASB officials responded that risks could include an improper payment made against a dormant contract or outstanding balances due to the FDIC or a contractor associated with a dormant contract. ASB officials indicated there are also safeguards in place that should address risks associated with dormant contracts, such as (1) the contract specialist and OM review the entire invoice before it is approved or rejected and processed for payment to ensure it involves an active contract and (2) the contract closeout process involves a reconciliation and verification that both parties to the contract have fulfilled their contract obligations and there are no open issues or responsibilities remaining. We did not test the safeguards related to the close-out process as part of our evaluation.
We confirmed with a procurement services consultant3 that most agencies rely on the knowledge of acquisition staff when evaluating new procurement requests for duplication and determining any continuing need for existing contracts. The procurement consultant indicated that evaluating contracts for duplication and continuing need is a legitimate concern for most agencies, especially agencies with a distributed, or non-centralized, contracting environment. Some agencies address this issue by having Contracting Officers specialize in separate areas. The procurement consultant was not aware of any sophisticated contract management system in the acquisition industry to identify duplicate requirements.
In that regard, DOA is developing a new automated procurement system (APS) which it plans to implement by May 2008. ASB representatives indicated that the APS system will include query capabilities and ad-hoc reporting capabilities that will assist contracting officers with identifying duplicative contracts. DOA provided us with the APS requirements traceability matrix, and we confirmed the matrix shows that there are a number of system requirements associated with query capability and reporting. In addition, ASB officials advised us that they intend to provide training to users regarding the manner in which contracts are described in APS data fields to take full advantage of the system’s search and reporting capabilities.
Contract Rationalization Mechanisms Appear to Be Working for DRR Contracts
To test the FDIC’s mechanisms for avoiding contract duplication and assessing continuing need, we evaluated existing DRR contracts. We judgmentally selected 39 of 61 contracts with a total value of $62.2 million.4 Our evaluation of the statements of work related to the 39 contracts showed that these contracts were generally not duplicative of other corporate contracts and addressed a continuing need of the Corporation.
During our review, we also learned that DRR has drafted a Long-Term Strategic Plan, dated January 2007, which includes a contracting goal to establish a comprehensive contracting strategy with objectives to (1) Establish a DRR program to ensure contracts are in place to maintain readiness and (2) Review DRR contracting management policy and make revisions as necessary. Table 1 below presents relevant excerpts from the Plan.
Table 1: Excerpts from DRR’s Long-Term Strategic Plan
Deliverable
|
Estimated Target Date
|
- Reviewing all DRR contracts and determining if addlitional contracts are needed to maintain readiness.
|
September 2007
|
- Defining short- and long-term contracting priorities
|
October 2007
|
- Establishing a process for continuous review of contracting needs
|
March 2008
|
This plan should provide a sound mechanism for assessing existing and planned contracts for duplication and continuing need.
Other Matters
We identified two recurring system-related issues that may hinder ASB’s ability to evaluate contracts for continuing need or duplication. First, contracting activity reports from NFE’s procurement module continue to contain inaccuracies. Second, important contract documents associated with the DRR contracts in our sample were missing from CEFile, the FDIC’s official contracting file repository. We, DOA’s Management Services Staff, and DRR Internal Review have previously reported and/or made recommendations on both issues, and ASB has reported that sufficient corrective actions have been taken to close most of the recommendations. Finally, the contract management system (i.e., contracting activity reports) and CEFile were identified as non-material or second-tier issues—areas where improvements can be made—as a result of the Corporation’s 2006 assurance statement process5. Nevertheless, the issues to some extent had not been resolved at the time we conducted our evaluation. A brief discussion regarding both issues follows.
NFE Reporting
In a prior evaluation report dated September 20066, the OIG recommended that DOA work with DOF and DIT to promptly correct inaccuracies in the Alert Report and Purchase Order Summary Report and resume distribution of corrected informational reports to Contracting Officers and Contract Specialists. According to the Internal Risk Information System (IRIS),7 DOA, DOF and DIT worked together to identify needed reporting query changes necessary to improve reporting accuracies and closed the recommendation. However, based on our analysis of NFE reports, we noted that deficiencies in the Purchase Order Summary Report persist. We found instances where the department identification, oversight manager’s division, and the responsible oversight manager fields in the report were not always accurate. The DRR Internal Review Unit found similar issues when it performed its review in April 2007. According to the DRR internal review report, the Purchase Order Summary Report typically contains incomplete and inaccurate data that requires manual changes in order to identify all DRR contracts and task orders. During our review, we confirmed with DRR staff that NFE reports were still requiring significant manual intervention to compile a complete and accurate listing of DRR contracts. DRR is currently working with DOA and OMs to correct the data quality issues. Although we are not making a recommendation, it is important that these issues be resolved to facilitate effective contract administration.
Missing CEFile Data
We also found that statements of work for 17 of the 39 DRR contracts that we selected for review were not entered into CEFile, although the two responsible contracting officers were able to provide us with hard copies. CEFile is the FDIC’s official electronic contract file of record and its use is required by all acquisition personnel in the Headquarters and Regional Contracting Offices. CEFile is a Web-based template utility on the FDICnet used to create official purchase orders and contract files and to electronically organize and store contractual documents in the FDIC Digital Library8. The CEFile should document the basis for the acquisition and the award, the assignment of contract administration, and any subsequent actions taken by ASB. ASB issued interim Acquisition Policy Number 2004-05, which states that it is the responsibility of both the contract specialist and the oversight manager to ensure that their CEFile is current, accurate, and complete.
As stated in Acquisition Policy Number 2004-05, the CEFile must be sufficient to constitute a complete history of the transaction for the purpose of (a) providing a complete background as a basis for informed decisions at each step in the acquisition process; (b) supporting actions taken; (c) providing information for reviews and investigations; and (d) furnishing essential facts in the event of litigation or congressional inquiries.
We discussed this issue with DOA officials, and they indicated there is a lack of available administrative support to assist the two contracting officers with updating CEFile for DRR contracts. Further, these officials told us they have a taken a number of steps to ensure that CEFile has been updated and they maintained that the instances we found were isolated to DRR contract files.
In our previously referenced report (Report No. 06-026, dated September 2006), we made several recommendations to address findings related to CEFile. Table 2 on the following page presents the status of these recommendations.
Rec. #
|
Recommendations
|
Corrective Actions Taken
|
Status
|
4 |
Reiterate to all acquisition personnel, including OMs, the requirement to use CEFile to record contract documentation and events. |
ASB issued a memo dated 10/18/06 to FDIC contracting officers and oversight managers reminding these officials of the requirement to maintain contract file documentation in CEFile. ASB also issued a revised Letter of Oversight Manager Confirmation (FDIC 3700/22 (10-06)). |
Completed |
5 |
Issue guidance to Contract Specialists and OMs that lists specific contracting documents and contracting events that should be recorded in CEFile and standardizes the organization and location of required documents within CEFile. |
On December 26, 2006, the Assistant Director, ASB, sent a memorandum to all FDIC contracting officers and oversight managers. The memorandum provided updated guidance for standardizing the organization and location of required documents within CEFile. |
Completed |
6 |
Establish an internal quality review program or process for routinely monitoring CEFile to ensure completeness of individual contract file contents.
|
ASB sent an e-mail dated December 28, 2006 to remind ASB’s section chiefs that a quarterly review was scheduled for January 2007 and that CEFile will be reviewed to ensure documentation is present and that it adequately supports the actions taken (post-award review).
|
Completed |
As shown, DOA has reported and we confirmed that corrective actions were taken to address all three recommendations. In addition, because our testing was limited to DRR contracts, we have no basis to know whether the deficiencies we noted extend to other divisions’ contracts. As a result, in lieu of making a recommendation, we provided DOA a listing of those contracts lacking statements of work in CEFile, and DOA officials agreed to promptly upload the documents into the system.
|